Skip to content

Conversation

@kingcody
Copy link
Member

@kingcody kingcody commented Sep 6, 2015

@kingcody kingcody added this to the 3.0.0 milestone Sep 6, 2015
app/generator.js Outdated
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Awk34 I'm wondering if we even need to be setting the defaults here. I assume they are for migration purposes, can you think of any other reasons, use cases?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think you're right. I can't think of any other purpose either.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here a5edbcd

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, test fix? Try removing that code and running the tests.

@kingcody kingcody force-pushed the fix/force-new-config branch from f5177f7 to b370180 Compare September 7, 2015 03:11
@kingcody
Copy link
Member Author

kingcody commented Sep 7, 2015

All checks out, probably since I update the fixtures config earlier to be 3.x.x compliant.

@Awk34
Copy link
Member

Awk34 commented Sep 7, 2015

👍

Awk34 added a commit that referenced this pull request Sep 7, 2015
fix(gen): force config update when it exists and `skipConfig == false`
@Awk34 Awk34 merged commit 06d0d28 into angular-fullstack:canary Sep 7, 2015
@kingcody kingcody deleted the fix/force-new-config branch September 9, 2015 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants